Business Analyst Community & Resources | Modern Analyst

Provenance Requirements Template

adrian — Sat, 07 Feb 2026 23:14:00 GMT

A practical, copy/paste Provenance Requirements Template for business analysts, systems analysts, and product managers building AI-enabled features. Use it to specify “Why should I believe this?” as testable requirements: citations and sources, freshness SLAs, confidence/uncertainty behavior, conflict handling, “what changed” explanations, and audit export fields. Includes ready-to-fill tables and a minimum set of validation tests so provenance becomes shippable product behavior—not a vague guideline.

Guardrails Catalog Template (with Starter Examples)

adrian — Sun, 25 Jan 2026 21:59:00 GMT

A copy/paste Guardrails Catalog you can use to turn vague AI “be safe” guidance into testable Allowed / Not Allowed requirements. Includes a blank catalog table plus 10 starter guardrails written in acceptance-criteria style (forbidden actions, restricted data, safe defaults, refusal wording, and validation steps). Designed for business analysts, systems analysts, and product managers shipping AI-enabled features.

Requirements-Friendly Data Dictionary Template

adrian — Sun, 07 Dec 2025 23:03:00 GMT

This template is intended to support capturing data requirement details (about Records and Fields) as part of the process of eliciting detailed functional requirements for an Information System.

It was developed in conjunction with the Trips-R-You Web-Based Flight Reservation System Case Study and Requirements In Context series of articles.

The fifth article in that series specifically discusses using this type of data dictionary.

The Trips-R-You Case Study Data Dictionary utilizes this template and includes over 150 example entries.

COTS Information System Detailed Requirements Template

adrian — Sun, 16 Jun 2024 23:43:00 GMT

This spreadsheet-based template is intended to support documenting detailed requirements (DTRs) discussed in the article “What Requirements Are Needed When Implementing a COTS Information System?"

A business analyst is normally expected to document requirements by describing what is needed, avoiding how a solution might satisfy them. But a selected COTS product is an existing solution. A domain-specific information system solution includes user interface (UI), data import, export, report, or automated function capabilities. Additionally, a COTS product’s selection may have been influenced in part by its inclusion of domain-independent capabilities such as configurable workflows or business rules.

A complete set of DTRs identifies which “Out-of-the-Box” (OOTB) capabilities are to be implemented as is, which need changing, which aren’t needed, and which unsupported capabilities need to be added.

The article "What Requirements Are Needed When Selecting a COTS Information System?” discusses capability-specific high-level requirements (HLRs). Those requirements are intended to be of the “What, not How” variety.

Requirements in Context – Tool Extension Meta-Model

adrian — Sat, 06 Mar 2021 23:44:00 GMT

The purpose of this spreadsheet is to present details of a meta-model that can and has been used to extend Requirements Management (RM) or Application Lifecycle Management (ALM) tools. The rationale for applying these extensions is discussed in the article: Tool Support for Managing Requirements [In Context]

BABOK 3.0 Tasks vs. Techniques

snikookar — Tue, 20 Oct 2020 04:49:00 GMT

This poster provides information related to the BABOK® 3.0 Tasks vs.Techniques. This is version 2 of this poster with better quality and printable (PDF).

This poster is useful for people who want to learn about the BABOK® standard and prepare for the IIBA® exams as well as people who want to use BABOK® in their work.

Trips-R-You Case Study: Data Import Requirements Example

adrian — Mon, 10 Feb 2020 00:09:00 GMT

The purpose of this spreadsheet is to present an example of detailed requirements for a data import interface. The example is part of the Trips-R-You Flight Booking Case Study. It's purpose is to provide an integrated, end-to-end set of requirement examples.

Trips-R-You Case Study: Data Export Requirements Example

adrian — Sun, 09 Feb 2020 23:59:00 GMT

The purpose of this spreadsheet is to present an example of detailed requirements for a data export interface. The example is part of the Trips-R-You Flight Booking Case Study. It's purpose is to provide an integrated, end-to-end set of requirement examples.

Trips-R-You Case Study: User Interface Example

adrian — Mon, 02 Dec 2019 00:36:00 GMT

The purpose of this spreadsheet is to present an example of detailed specifications for a screen-based user interface. The example is part of the Trips-R-You Flight Booking Case Study. It's purpose is to provide an integrated, end-to-end set of requirement examples.

The following case study example high-level requirements identify the need for this user interface:

Trips-R-You Case Study: Requirements

adrian — Sun, 29 Sep 2019 20:04:00 GMT

The purpose of this spreadsheet is present an integrated, end-to-end set of requirement statement examples, based on the Trips-R-You Case Study. In IIBA® BABOK® V3 terminology, end-to-end means from Business Requirements to Stakeholder Requirements to Solution and Transition Requirements. The case study, and associated artifacts, use the more traditional business terms Goals, High-level Requirements (HLRs), and Detailed Requirements.

Basics of Product and Process Requirements

adrian — Wed, 18 May 2016 06:08:00 GMT

Requirements are fundamental in business analysis and creating enterprise solutions. Due to the important role it plays, requirements and requirements engineering have been continuously emphasized in various business organizations.

Requirements Document Generation App (for iPad)

busyindc — Sun, 08 Mar 2015 13:24:00 GMT

The tool allows Business Analysts to gather and document and generate the Business Requirements Document in real time, and the ability to work on multiple projects simultaneously.

Enjoy the free iPad app. just search for "Requirements Ninja" on iPad. I hope it makes requirements gathering a little bit more fun!

BABOK 2.0 Snapshots

snikookar — Sun, 05 Jan 2014 12:27:00 GMT

This is a package includes seven snapshots which cover Knowledge Areas and Underling Competencies in BABOK v2.0.

BABOK 2.0 - The Big Picture

adrian — Sat, 21 Apr 2012 05:56:00 GMT

BABOK 2.0 - The Big Picture

BABOK 2.0 Tasks, Inputs, and Outputs

adrian — Sat, 21 Apr 2012 05:34:00 GMT

BABOK 2.0 Tasks, Inputs, and Outputs

Requirements Document Template for Software Development Projects

host — Sun, 29 Jan 2012 07:40:00 GMT

The goal of this template is to provide you with useful suggestions for the documentation of software requirements in a development project. If you already use or must use another - internal or industry-specific - type of document or template, we hope you will still find useful ideas inside this document. For folks who are already in the midst of an existing project this template may also be used as a checklist for various aspects of requirement documentation.

Requirements SL-07 - Template with Examples

adrian — Sat, 21 Jan 2012 19:20:00 GMT

Business Analysts, IT developers and consultants often ask for sample requirements specification as a starting point in their specific project. This document is such a specification. It is a template filled out with a complex example: requirements for an Electronic Health Record system (EHR).

Requirements Traceability Matrix

jennifercolburn — Thu, 20 Oct 2011 21:12:00 GMT

At a recent presentation I gave to Project Manager's regarding BA's, they were very interested in seeing a Requirements Traceability Matrix.

CBAP Prep -> BABOK V2.0 Mindmap: Knowledge Areas and Associated Tasks, Inputs and Outputs

adrian — Mon, 11 Apr 2011 03:53:00 GMT

Great CBAP Preparation Resource: Expandable BABOK V2.0 Mindmap including Knowledge Areas and Associated Tasks, Inputs and Outputs

Getting Started with Process Improvement: 18 Page Guide

derweeks — Thu, 06 Jan 2011 16:32:00 GMT

You know there are opportunities to improve your existing processes and we want to help you get started. This 18-page Guide highlights key steps and success factors that can be applied to your next process improvement project.

Tech Spec Traceability Matrix

admin — Wed, 20 May 2009 08:02:00 GMT

I have attached the instructions for a Tech Spec Traceability Matrix.

Example: Requirements Pack - Passenger Movements

host — Tue, 15 Jul 2008 06:53:00 GMT

This is a sample System Requirements Specification document (SRS) for a "Passenger Movements" module which part of a system for a fictitious company.

Terms of Reference Template

host — Tue, 15 Jul 2008 06:31:00 GMT

Terms of reference document describes the purpose and structure of a project, committee, meeting, negotiation, etc. When used in relation to a project, the doc is also known as a project charter.

Volere Atomic Requirements Template

adrian — Tue, 17 Jun 2008 05:15:00 GMT

The Volere Snow Card is a great way to capture the various attributes of a specific (atomic) requirement. Print this out and use it in your own requirements gathering workshop.